How this site is built for accessibility

The standard we’re building towards

We build this site towards WCAG 2.2, level AA — the widely used standard for how accessible a website should be. No one outside this project has independently audited our work against it yet, so this page says built towards, not meets or conforms to. That distinction stays on this page until an outside check has actually been done.

What we’ve actually checked

On 11 September 2026 the site was gone through by hand, page by page, and the following was checked and confirmed:

• Body text is set at 17 pixels or larger across the site, rather than shrunk down to fit more onto the page. (One page steps to 16.5 pixels on the narrowest phones; it is on the list.)
• Every control on the site — buttons, tick-boxes, the file drop area, the page-count slider — is built to be reached and used with a keyboard alone, and shows a visible outline around whatever currently has focus.
• The tick-boxes are real checkboxes with a real label attached to each one, not a shape built to look like a tick-box.
• If a phone or computer is set to reduce motion, this site turns its own animations off.
• Colour is never the only way something is shown. A route that’s been found also carries its name; a deadline also carries a date; nothing on this site relies on red or green alone.
• The diagrams that carry real information — the ones showing how a read works — have a written description built in for a screen reader. Purely decorative touches, such as the paper texture and the scattered pile of documents on the opening screen, are hidden from a screen reader so they don’t get in the way.
• Headings run in order down most of the site, so a screen reader can move between sections by heading level. One place was found where a level was skipped, on the first screen of the tool — it’s on the list to put right.

What we haven’t tested yet

Some things haven’t been done yet, and this page isn’t going to pretend otherwise:

• Reading the site through with a real screen reader, such as NVDA, JAWS or VoiceOver.
• Using it on a real phone, rather than a simulated one.
• Walking through every step of the tool using only a keyboard, start to finish, rather than checking individual controls on their own.

These are on the list.

Tell us about a problem

This page is checked by us, not by an outside auditor, so it will miss things. If something on this site doesn’t work with whatever you use to read it — a screen reader, a keyboard, a magnifier, anything else — we want to know about it.

Keeping this page current

Prepared 11 September 2026. Last checked 11 September 2026. When the site changes, or when it is checked again, the date at the top of this page changes with it.